View UPD6708CX_782100.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

mos integrated circuit m pd6708 iebus ? (inter equipment bus ? ) protocol control lsi document no. u10680ej2v0ds00 (2nd edition) (previous no. ic-3282) date published january 1996 p printed in japan data sheet the information in this document is subject to change without notice. the mark h shows major revised points. description the m pd6708 is a peripheral lsi for microcontrollers that controls the protocol of the iebus. this lsi processes the protocol of the iebus. because it is provided with a transmit/receive buffer, the microcontroller can concentrate on the application processing of the iebus. because the m pd6708 also contains an iebus driver/receiver, it can be directly connected to the bus. features protocol control of iebus ? multi-master system ? broadcast communication function (commu- nication between one unit and multiple units) ? choice of three modes with different trans- mission speeds at 12 mhz at 12.58 mhz mode 0 approx. 3.9 kbps approx. 4.1 kbps mode 1 approx. 17 kbps approx. 18 kbps mode 2 approx. 26 kbps approx. 27 kbps ordering information part number package m pd6708cx 16-pin plastic dip (300 mil) m pd6708gs 16-pin plastic sop (300 mil) on-chip iebus driver/receiver transmit/receive buffer transmit: 4-byte fifo receive: 20-byte fifo interface with microcontroller ? three-line serial i/o (sck, so, si pins) ? transfer with msb first oscillation frequency (f x ): 12 mhz, 12.58 mhz ? in modes 0 and 1: 1.5 % ? in mode 2: 0.5 % supply voltage: v dd = 5 v 10 % application field fields where a small-scale digital data transfer system is required between equipment, such as automobile electronic systems and industrial equipment 1993
2 m pd6708 pin configuration (top view) ? 16 pin plastic dip (300 mil) m pd6708cx ? 16 pin plastic sop (300 mil) m pd6708gs sck : serial clock input si : serial data input so : serial data output irq : interrupt request output r/w : read/write switchover input xi, xo : system clock gnd : ground busC, bus+ : iebus input/output av dd : iebus analog power supply (connected to v dd pin) c/d : command/data switchover input cs : chip select input reset : reset input test : test input (connected to v dd pin) v dd : positive power supply sck si so irq r/w xi xo gnd v dd test reset cs c/d av dd bus+ bus 16 15 14 13 12 11 10 9 1 2 3 4 5 6 7 8
3 m pd6708 contents 1. pin functions ............................................................................................................................... .......... 5 1.1 list of pin functions ............................................................................................................................... .......... 5 2. iebus operation ............................................................................................................................... ..... 6 2.1 operation overview ............................................................................................................................... ............ 6 2.2 iebus communication protocol ...................................................................................................................... 7 2.2.1 bus mastership determination (arbitration) ................................................................................... 8 2.2.2 communication modes ...................................................................................................................... 8 2.2.3 communication address ................................................................................................................... 9 2.2.4 broadcast communication ................................................................................................................ 9 2.3 transfer protocol ............................................................................................................................... .............. 10 2.4 transfer data (contents of data field) ......................................................................................................... 16 2.5 bit format ............................................................................................................................... .......................... 19 3. internal configuration ................................................................................................................. 20 3.1 data link layer controller ............................................................................................................................. 21 3.2 physical layer controller ............................................................................................................................... 21 3.3 iebus driver/receiver ............................................................................................................................... ...... 21 3.4 host interface ............................................................................................................................... .................... 21 4. interfacing with host controller .......................................................................................... 22 4.1 accessible buffers and registers from host controller ........................................................................... 22 4.1.1 write data buffer (wdb) .................................................................................................................. 22 4.1.2 read data buffer (rdb) ................................................................................................................... 22 4.1.3 command register (cmr) ................................................................................................................ 22 4.1.4 status register (str) ....................................................................................................................... 23 4.2 host interface modes ............................................................................................................................... ....... 23 4.2.1 switching through pin control ....................................................................................................... 24 4.2.2 switching through software control .............................................................................................. 26 4.3 reset mode ............................................................................................................................... ........................ 28 5. communication control commands ......................................................................................... 30 5.1 overview of communication control commands ....................................................................................... 30 5.2 communication control command functions ............................................................................................ 31 5.2.1 init command (command code: 0000) .......................................................................................... 31 5.2.2 setsa command (command code: 0001) .................................................................................... 32 5.2.3 mreq1 command (command code: 0010) ................................................................................... 33 5.2.4 mreq2 command (command code: 0011) ................................................................................... 34 5.2.5 abort command (command code: 0100) ................................................................................... 34 5.2.6 setsd command (command code: 0101) .................................................................................... 35 5.2.7 getsta command (command code: 0110) .................................................................................. 36 5.2.8 setrev command (command code: 0111) .................................................................................. 37 6. return codes ............................................................................................................................... ....... 38 6.1 return codes in master/slave data transmission ..................................................................................... 38 6.2 return codes in master reception ............................................................................................................... 38 6.3 return codes in slave reception ................................................................................................................. 39 6.4 return codes in broadcast reception ......................................................................................................... 39 6.5 return codes generation intervals ............................................................................................................... 40 7. communicating with host controller ................................................................................... 43 7.1 master transmission ............................................................................................................................... ........ 43 7.1.1 master transmission by mreq1 command .................................................................................. 43 7.1.2 master transmission by mreq2 command .................................................................................. 44
4 m pd6708 7.2 slave transmission ............................................................................................................................... .......... 44 7.2.1 data transmission ............................................................................................................................ 44 7.2.2 transmitting slave status address and lock address ................................................................. 45 7.3 master reception ............................................................................................................................... .............. 45 7.4 slave reception ............................................................................................................................... ................ 46 7.5 broadcast reception ............................................................................................................................... ........ 47 8. example of host controller processing flow ................................................................ 48 8.1 main routine ............................................................................................................................... ...................... 48 8.2 interrupt service routine ............................................................................................................................... .49 8.3 processing routine ............................................................................................................................... .......... 50 8.3.1 m pd6708 initialization routine ......................................................................................................... 50 8.3.2 communication control command processing routine .............................................................. 51 8.3.3 master transmission processing routine ...................................................................................... 57 8.3.4 slave data transmission processing routine ............................................................................... 58 8.3.5 master reception processing routine ............................................................................................ 59 9. electrical specifications ............................................................................................................ 63 10. package drawings ............................................................................................................................ 67 11. recommended soldering conditions ....................................................................................... 69 appendix major differences between m pd6708 and m pd72042a, m pd72042b ................... 70
5 m pd6708 1. pin functions 1.1 list of pin functions pin no. pin name input/output function i/o format at reset 1 sck input input for serial clock used to interface with microcontroller. cmos input input 2 si input input for serial data used to interface with microcontroller. cmos input input 3 so output output for serial data used to interface with microcontroller. cmos output high level 4 irq output output used by interrupt request signals generated by cmos output low level communication and command execution results. used as operation start request signal to microcontroller. the interrupt request signal is output for 8 m s or longer at high level. 5 r/w input input for switching serial interface read/write mode. cmos input input when high, it is in the read mode. when low, it is in the write mode. when this pin is low and c/d pin high, the read and write modes can be switched by commands input from the serial interface. 6 xi CC connection pins for system clock resonator. CC (oscillation 7 xo use a 12- or 12.58-mhz crystal, or ceramic resonator. continues) frequency precision depends on the communication mode used. mode 0 : 1.5 % mode 1 : 1.5 % mode 2 : 0.5 % 8 gnd CC ground CC CC 9 busC input/output input/output for iebus. CC high 10 bus+ impedance 11 av dd CC iebus driver/receiver analog power supply. connect to v dd . CC CC 12 c/d input input used to switch between processing data input to the cmos input input serial interface as commands or data. when set to high, data is processed as commands; when low, data is processed as data. when this pin is high and r/w pin low, the read and write modes can be switched by commands input from the serial interface. 13 cs input chip select input. cmos input input when low, serial interface input is enabled. when high, serial clock (sck) input is disabled, so pin becomes high impedance, and the serial clock counter is reset. the status of cs pin is not affected by iebus transmit and receive operations. 14 reset input system reset signal input pin. cmos input input low input effects a reset. always input the low signal for 6 m s or longer after turning on the power. 15 test input always connect this pin to the v dd . cmos input CC 16 v dd CC positive power supply input. apply a voltage of 5 v 10 %. CC CC
6 m pd6708 2. iebus operation 2.1 operation overview the m pd6708 is an iebus interface cmos lsi device. the iebus is a bus for a small-scale digital data transfer system designed to transfer data between electronic devices. the m pd6708 is connected to a microcontroller incorporated in electronic equipment with a serial interface (sck, so, si pins). the data and commands required to transfer data with the host controller (microcontroller) are set via this serial interface. when the host controller transmits data to the m pd6708 via the serial interface, signals are output from the bus pins (bus+ and busC). data received from the bus pins can be read by the host controller via the serial interface. h
7 m pd6708 2.2 iebus communication protocol an overview of the iebus is as follows. ? communication system: half-duplex asynchronous communication ? multi-master system all the units connected to the iebus can transfer data to the other units. ? broadcast communication function (communication between one unit and multiple units) group broadcast communication: broadcast communication with group units general broadcast communication: broadcast communication with all units. ? three modes with different transfer speeds selectable. f x = 12 mhz f x = 12.58 mhz maximum number of transfer bytes (bytes/frame) mode 0 approx. 3.9 kbps approx. 4.1 kbps 16 mode 1 approx. 17 kbps approx. 18 kbps 32 mode 2 approx. 26 kbps approx. 27 kbps 128 ? access control: csma/cd (carrier sense multiple access with collision detection) the priority order for bus occupancy is as follows. <1> broadcast communication takes precedence over ordinary communication (i. e., communication between one unit and another). <2> the lowest master address has the highest priority. ? communication scale number of units: max. 50 cable length: max. 150 m (with twisted-pair cable ) load capacity: max. 8000 pf , f x = 12 mhz max. 7100 pf , f x = 12.58 mhz terminating resistor: 120 w h
8 m pd6708 2.2.1 bus mastership determination (arbitration) when a unit connected to the iebus controls another unit, it performs an operation to occupy the bus. this operation is called arbitration. arbitration is to select one unit, and if several units begin to transmit data simultaneously, gives permission to occupy the bus to that one unit. so that one unit is granted the permission to occupy the bus as a result of the arbitration, the following priority conditions are determined. remark the units not given permission through arbitration are automatically allowed to get into retransfer mode (number of retransfer times for the m pd6708: 3). (1) priority according to type of communication broadcast communication (between a single and multiple units) takes precedence over ordinary communication (between single units). (2) priority according to master address if the communication devices are of the same type, the unit with the lowest master address has the highest priority. example the master address comprises 12 bits, and unit 000h has the highest priority while unit fffh has the lowest priority. 2.2.2 communication modes the iebus is provided with three communication modes with different transfer speeds. the transfer speed and maximum number of transfer bytes in a single communication frame in each communication mode are shown in table 2-1. table 2-1. transfer speed and maximum number of transfer bytes in each communication mode communication mode maximum number of transfer bytes (bytes/frame) actual transfer speed note 1 (kbps) f x = 12 mhz note 2 f x = 12.58 mhz note 2 0 16 approx. 3.9 approx. 4.1 1 32 approx. 17 approx. 18 2 128 approx. 26 approx. 27 notes 1. actual transfer speed when the maximum number of bytes is transferred 2. oscillation frequency when the m pd6708 is used cautions 1. a communication mode is selected for each unit connected to the iebus before communication is performed. if the communication mode of the master unit is not the same as that of the unit with which the master unit is to communicate (slave unit), communication cannot be performed correctly. 2. if the oscillation frequency of one unit is fx = 12 mhz and that of the other unit is fx = 12.58 mhz, communication cannot be performed correctly even if the communication mode is the same. make sure that the oscillation frequencies of the two units to communicate are the same. h
9 m pd6708 2.2.3 communication address with the iebus, a 12-bit communication address is assigned to each unit. the communication address is made up as follows. higher 4 bits: group number (number which identifies the group to which the unit belongs) lower 4 bits: unit number (number which identifies a unit within a group) 2.2.4 broadcast communication in ordinary communication, there is only one master unit and one slave unit, and transmission or reception is performed on an one-to-one basis. in broadcast communication, however, there are a number of slave units and the master unit performs transmission with these slave units. because there are several slave units, no acknowledge signals is returned from the slave units during communication. whether broadcast communication or ordinary communication is performed is specified by the broadcast bit (for the broadcast bit, see 2.3 (1) <2> broadcast bit ). there are two kinds of broadcast communication, as follows. (1) group broadcast communication broadcast communication is performed to the units in a group whose group numbers are the same as that specified by the higher 4 bits of the communication address. (2) general broadcast communication broadcast communication is performed to all units irrespective of their group numbers. group broadcast communication or general broadcast communication is identified by the value of a salve address (for the slave address, see 2.3 (3) slave address field ). h
10 m pd6708 2.3 transfer protocol the iebus transfer signal format is shown in figure 2-1. data is transferred as a series of signals called a communication frame. the number of data that can be transferred in one communication frame and the transfer speed differ depending on the communication mode. figure 2-1. transfer signal format p: parity bit (1 bit) a: acknowledge bit (1 bit) when a = 0: ack when a = 1: nak n: number of data bytes remark in broadcast communication, the value of the acknowledge bit is ignored. (1) header a header comprises a start bit and a broadcast bit, as described below. <1> start bit the start bit is a signal which tells the other units that data transmission will start. the unit which is about to start transmitting data will output the low signal (the start bit) for a specified time, and then outputs the broadcast bit. if another unit is already outputting a start bit before one unit outputs a start bit, the unit will not output the start bit. it will wait until the another unit completely outputs the start bit, and then outputs the broadcast bit. the units other than the one that has started transmission detect this start bit and enters the reception state. <2> broadcast bit the broadcast bit distinguishes between broadcast communication and ordinary communication. when this bit is 0, it indicates broadcast communication; when it is 1, it indicates ordinary communication. there are two types of broadcast communication: group broadcast and general broadcast. these types are identified by the value of the slave address (for the slave address, see (3) slave address field ). in broadcast communication, there are a number of slave units. therefore, the acknowledge bit is not returned in the fields described in (2) below and onward. if two or more units start to transmit a communication frame simultaneously, broadcast communication takes precedence over ordinary communication, and wins in the arbitration. h field name number of bits transfer time mode 0 mode 1 mode 2 header master address field slave address field control field message length field data field 112 1 112 11411 811 811 811 start bit broad- cast bit master address p slave address p a control bit pa message length bit p a data bit p a data bit pa approx. 7330 s m approx. 2090 s m approx. 1590 s m approx. 1590 n s m approx. 410 n s m approx. 300 n s m (f x = at 12 mhz)
11 m pd6708 (2) master address field the master address field is used to transmit the unit address of the master unit (master address) to the other units. the master address field consists of master address bits and a parity bit. the master address comprises 12 bits and is output from the msb. if two or more units start transmitting the broadcast bit of the same value simultaneously, the arbitration decision is made by the master address field. the master address field compares the data the master has output with the data on the bus each time the master transmits 1 bit of data. if the master address output by the master unit is different from the data on the bus, the master unit assumes that it has lost in arbitration, stops transmission, and enters the reception state. because the iebus has a wired-and configuration, the unit having the lowest master address of the units participating in the arbitration (arbitration masters) wins in the arbitration. ultimately, only one unit remains in the transmission state as the master unit after outputting a 12-bit master address. this master unit then outputs a parity bit note , makes the other units confirm the master address, and then outputs the slave address field. note even parity is used. when the number of the bits that are 1 in the master address is odd, the parity bit is 1. (3) slave address field the slave address field is used to transmit the address (slave address) of a unit (slave unit) with which the master wishes to communicate. the slave address field consists of slave address bits, a parity bit, and an acknowledge bit. the slave address comprises 12 bits and is output from the msb. after the 12-bit slave address is transmitted, the parity bit is output to prevent the slave address from being received incorrectly. next, the master unit looks for the acknowledge signal (bit) from the slave unit to confirm that the slave unit exists on the bus. when the master unit detects the acknowledg e signal, it starts outputting the control field. in the case of broadcast communication, however, the master unit outputs the control field without waiting for the acknowledge bit. a slave unit outputs the acknowledge signal if it has detected that its slave address coincides with that selected by the master and that the parities of both the master and slave addresses are even. if the parity is odd, the slave unit assumes that the master or slave address has not been correctly received, and does not output the acknowledge signal. in this case, the master unit enters the standby (monitor) state and communication ceases. in the case of broadcast communication, the slave address is used to distinguish between group broadcast and general broadcast as follows: slave address = fffh: general broadcast communication slave address 1 fffh: group broadcast communication remark in the case of group broadcast communication, the group number is the value of higher 4 bits of the slave address. h
12 m pd6708 (4) control field the control field indicates the type of data and the transfer direction of the subsequent data field. the control field consists of 4 control bits, a parity bit, and an acknowledge bit. the control bits are output from the msb. a parity bit is output after the control bits. when the parity is even and the slave can execute the function requested by the master unit, the slave unit outputs an acknowledge signal, and then outputs the next message length field. if the slave unit cannot execute the function requested by the master unit even if the parity is even, or if the parity is odd, the sl ave unit does not output the acknowledge signal but returns to the standby (monitor) state. after the master unit has confirmed the acknowledge signal, it starts outputting the next message length field. if the master unit is cannot confirm the acknowledge signal, it enters the standby state and stops communication. in the case of broadcast communication, however, the master unit starts outputting the message length field without confirming the acknowledge signal. for the functions of the control bits, see table 2-3. (5) message length field the message length field is used to specify the number of communication data bytes. the message length field comprises 8 message length bits, a parity bit and, an acknowledge bit. the message length bits are output from the msb. the message length bits indicate the number of communication data bytes as shown in table 2-2. table 2-2. meaning of message length bits message length bits (hex) number of transmission data bytes 01h 1 byte 02h 2 bytes :: :: ffh 255 bytes 00h 256 bytes remark in the communication mode, if the number of bytes exceeding the maximum number of transfer bytes per frame is set, two or more frames are communicated. in this case, the message length bits indicate the number of remaining communication data bytes during the second communication and onward. the operation of this field differs depending on whether the master transmits (bit 3 of control bits is 1) or receives (bit 3 of control bits is 0) data. <1> when master transmits data the message length bits and parity bit are output by the master unit. the slave unit outputs the acknowledge signal and then the next data field if it detects that the parity is even. the slave unit does not output the acknowledge signal in the case of broadcast communication. if the parity is odd, the slave unit assumes that the message length bits have not been received correctly, and returns to the standby (monitor) state without outputting the acknowledge signal. in this case, the master unit also returns to the standby state, and communication ceases. h
13 m pd6708 <2> when master receives data the message length bits and parity bit are output by the slave unit. the master unit outputs the acknowledge signal if it detects that the parity bit is even. if the parity is odd, the master unit assumes that the message length bits have not been received correctly, and returns to the standby state without outputting the acknowledge signal. in this case, the slave unit also returns to the standby state, and communication ceases. (6) data field the data field is used to transmit/receive data to/from the slave units. the master unit uses the data field to transmit data to and receive data from the slave units. the data field consists of 8 data bits, a parity bit, and an acknowledge bit. the data bits are output from the msb. following the data bits, the parity bit and acknowledge bit are output from the master unit and the slave unit, respectively. broadcast communication is performed when only the master unit transmits data. at this time, the acknowledge signal is ignored. the operation differs depending on whether the master performs transmission or reception, as follows. <1> when master transmits data when the master unit writes data to the slave unit, the master unit transmits data bits and a parity bit to the slave unit. the slave unit receives the data bits and parity bit. if the parity is even and the receive buffer is empty, the slave unit outputs the acknowledge signal. if the parity is odd and the receive buffer is not empty, the slave unit denies acknowledgment of the corresponding data and does not output the acknowledge signal. if no acknowledge signal is output from the slave unit, the master unit transmits the same data again. the master unit continues this operation until it detects the acknowledge signal from the slave unit or the data reaches the maximum number of transfer bytes. if the parity is even and the acknowledge signal has been output from the slave unit, and if the master unit has more data to transmit and the maximum number of transfer bytes is not exceeded, the master unit will transmit the next data. in the case of broadcast communication, the slave unit does not output the acknowledge signal, and the master unit transfers data on a byte-by-byte basis. <2> when master receives data when the master unit reads data from the slave unit, the master unit outputs synchronization signals corresponding to all the read bits. the slave unit outputs the contents of the data and parity bits onto the bus in accordance with the synchronization signals from the master unit. the master unit reads the data and parity bit output by the slave unit, and checks the parity. if the parity is odd or the receive buffer is not empty, the master unit denies acknowledgement of that data and does not output the acknowledge signal. if the data is within the maximum number of transfer bytes that can be transmitted in one frame, the master unit repeatedly reads the same data. if the parity is even and the receive buffer is empty, the master unit acknowledges the data and transmits back the acknowledge signal. if the data is within the maximum number of bytes that can be transmitted in one frame, the master unit reads the next data. h h
14 m pd6708 (7) parity bits parity bits are used to check that there is no error in the transfer data. a parity bit is added to the master address bits, slave address bits, control bits, message length bits, and data bits. even parity is used. if the number of the bits that are 1 bits in data is odd, the parity bit is 1, and if the number of t he bits that are 1 bits is even, the parity bit is 0. (8) acknowledge bits in ordinary communication (between two units), an acknowledge bit is added to the following places to confirm that data has been acknowledged correctly. ? at the end of the slave address field. ? at the end of the control field. ? at the end of the message length field. ? at the end of a data field. the definition of the acknowledge bit is as follows. ? 0: indicates that transfer data has been acknowledged (ack). ? 1: indicates that transfer data has not been acknowledged (nak). note that the value of the acknowledge bit is ignored in broadcast communication. <1> acknowledge bit at the end of the slave field when any of the following conditions is met, the acknowledge bit at the end of the slave field is nak, and communication is discontinued. ? if the parity of the master address bits or slave address bits is incorrect. ? if a timing error (error in bit format) occurs. ? if the slave unit does not exist. <2> acknowledge bit at the end of the control field when any of the following conditions is met, the acknowledge bit at the end of the control field is nak, and communication is discontinued. ? if the parity of the control bits is incorrect. ? if bit 3 of the control bits is 1 (write operation) when the slave receive buffer note is not empty. ? if the control bits indicate read operation (3h or 7h) when the slave transmit buffer note is empty. ? if 3h, 6h, 7h, ah, bh, eh, or fh of control bits is requested from a unit other than the unit which set the lock when a lock has been set. ? if the control bits indicate lock address read (4h) when a lock has not been set. ? if a timing error occurs. ? if the control bits are undefined. note see 2.4 (1) reading slave status (ssr) (control bit: 0h, 6h) . h
15 m pd6708 <3> acknowledge bit at the end of a message length field when either of the following conditions is met, the acknowledge bit at the end of the message length field is nak, and communication is discontinued. ? if the parity of the message length bits is incorrect. ? if a timing error occurs. <4> acknowledge bit at the end of a data field when any of the following conditions is met, the acknowledge bit at the end of a data field is nak, and communication is discontinued. ? if the parity of the data bits is incorrect note . ? if a timing error occurred in or after the previous acknowledge bit transmission. ? if the receive buffer is full and cannot accept any more data note . note in this case, if the number of transfer bytes is within the maximum number of bytes which can be transmitted, the transmitting side re-executes transmission of that data field.
16 m pd6708 2.4 transfer data (contents of data field) the contents of the data field are data specified by the control bits. table 2-3. functions of control bits bit 3 note 1 bit 2 bit 1 bit 0 function note 2 0h 0 0 0 0 reads slave status (ssr) 1h 0 0 0 1 undefined 2h 0 0 1 0 undefined 3h 0 0 1 1 reads and locks data 4h 0 1 0 0 reads lock address (lower 8 bits) 5h 0 1 0 1 reads lock address (higher 4 bits) 6h 0 1 1 0 reads and unlocks slave status (ssr) 7h 0 1 1 1 reads data 8h 1 0 0 0 undefined 9h 1 0 0 1 undefined ah 1 0 1 0 writes and locks command bh 1 0 1 1 writes and locks data ch 1 1 0 0 undefined dh 1 1 0 1 undefined eh 1 1 1 0 writes command fh 1 1 1 1 writes data notes 1. depending on the value of bit 3 (msb), the transfer direction of the message length bits of the subsequent message field and data field differs. when bit 3 is 1, data are transferred from the master unit to the slave unit. when bit 3 is 1, data are transferred from the slave unit to the master unit. 2. 3h, 6h, ah, and bh are control bits that specify locking or unlocking. if any of undefined values 1h, 2h, 8h, 9h, ch, or dh is transmitted, no acknowledge bit is returned. a unit locked by the master unit rejects acknowledging the control bits and does not output the acknowledge bit if the control bits received from the master unit which requested locking is in any other state than that shown in table 2-4. table 2-4. control field corresponding to locked slave unit bit 3 bit 2 bit 1 bit 0 function 0h 0 0 0 0 reads slave status 4h 0 1 0 0 reads lock address (lower 8 bits) 5h 0 1 0 1 reads lock address (higher 4 bits) h
17 m pd6708 (1) reading slave status (ssr) (control bit: 0h, 6h) the master unit can learn the reason why the slave unit has not returned the acknowledge bit (ack) by reading the slave status. the slave status is determined by the results of the last communication performed by the slave unit. all the slave units can provide slave status information. the meanings of the slave status are shown in table 2-5. figure 2-2. bit configuration of slave status (ssr) table 2-5. meanings of slave status bit value meaning bit 0 note 1 0 slave transmit buffer empty 1 slave transmit buffer is not empty. bit 1 note 2 0 slave receive buffer empty 1 slave receive buffer is not empty. bit 2 0 unit is not locked. 1 unit is locked. bit 3 0 fixed to 0 bit 4 note 3 0 slave transmission ends 1 slave transmission enabled bit 5 0 fixed to 0 bit 7 00 mode 0 indicates the highest mode the unit bit 6 01 mode 1 supports note 4 . 10 mode 2 11 for future expansion notes 1. the slave transmit buffer is the buffer accessed during data read processing (control bits: 3h, 7h). with the m pd6708, this buffer corresponds to the write data buffer (wdb) when the setsd command is valid (see 5.2.6 setsd command ). 2. the slave receive buffer is the buffer accessed during data write processing (control bits: 8h, ah, bh, eh, fh). with the m pd6708, this buffer corresponds to the read data buffer (rdb). 3. the value of bit 4 can be selected by init command (see 5.2.1 init command ). 4. because the m pd6708 can support mode 2, bits 7 and 6 are fixed at 10. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 msb lsb h
18 m pd6708 (2) transferring data command (control bit: read (3h, 7h), write (ah, bh, eh, fh)) during data read (3h, 7h), the data in the data buffer of the slave unit are read to the master unit. during data write (bh, fh) or during command write (ah, eh), the data the slave unit has received are processed according to the operation convention. remarks 1. the user can voluntarily select data and command as his system requires. 2. control bits 3h, ah, and bh may be locked depending on the communication condition and status. (3) reading lock address (control bits: 4h, 5h) when the lock address is read processing (4h, 5h), the address (12 bits) of the master unit that has issued the lock instruction is read in 1-byte units, as shown below. figure 2-3. lock address configuration (4) locking and unlocking (locking (3h, ah, bh), unlocking (6h)) the lock function is used to transfer a message over two or more frames. a locked unit receives data only from the unit that has locked the unit. locking and unlocking are performed as described below. <1> locking after the transmission/reception of the acknowledge bit 0 of the message length field by the control bits (3h, ah, bh) which specify the lock has ended, if the communication frame is completed without completing the transmission or reception of the number of data bytes specified by the message length bits, the slave unit is locked by the master unit. at this time, the bit (bit 2) relating to the locking of the byte which indicates the slave status is set to 1. <2> unlocking after completion of transmission or reception of data in one frame by the number of data bytes specified by the message length bits with control bits (3h, ah, or bh) specifying locking or control bits (6h) specifying unlocking, the slave unit is unlocked by the master unit. at this time, the bit (bit 2) relating to the locking of the byte which indicates the slave status is reset to 0. locking and unlocking are not performed in the case of broadcast communication. caution to unlock the unit specified to be unlocked by the unit itself, the init command (see 5.2.1 init command) must be executed with the m pd6708 (whether a unit is locked or not can be checked by using the getsa command (see 5.2.7 getsa command). h msb lsb lower 8 bits undefined higher 4 bits control bits : 4h control bits : 5h
19 m pd6708 2.5 bit format the iebus communication frame bit format (concept) is shown in figure 2-4. figure 2-4. iebus bit format (concept) logic 1: potential difference between bus lines (bus+ pin and busC pin) is 20 mv or lower (low level). logic 0: potential difference between bus lines (bus+ pin and busC pin) is 120 mv or higher (high level). preparation period: the first or subsequent low-level (logic 1) period synchronous period: the next high-level (logic 0) period data period: the period that expresses the bit value (logic 1: low level; logic 0: high level) the synchronous period and data period have approximately the same length. the iebus uses bit-by-bit synchronization. the specifications for the total bit time and the periods allocated to the bits depend on the type of transfer bit, and on whether the unit is the master unit or the slave unit. h preparation period synchronous period data period logic "1" logic "0" preparation period synchronous period data period
20 m pd6708 3. internal configuration the m pd6708 is composed of the following four blocks. (1) data link layer controller (2) physical layer controller (3) iebus driver/receiver (4) host interface figure 3-1. m pd6708 internal blocks data link layer controller receiver driver iebus driver/receiver filter bit sequencer physical layer controller host interface status register (str) read data buffer (rdb) 20 bytes write data buffer (wdb) 4 bytes command register (cmr) shift register serial i/o controller bus+ bus sck so si cs irq c/d r/w
21 m pd6708 3.1 data link layer controller the data link layer controller performs processing of the iebus protocol data link layer (frame composition and resolution, communication error detection, etc.), execution of communication control commands set by the host controller, and generate a return code that informs the host controller of the communication status. 3.2 physical layer controller the physical controller performs generation and resolution of bit timing and also converts the signals between the bus lines through the driver/receiver. 3.3 iebus driver/receiver the driver/receiver performs conversion between the logic signals within the m pd6708 and the iebus signals. the iebus signals and their relationship to the logic statuses are shown in table 3-1. table 3-1. relationship between iebus signals and logical statuses 3.4 host interface the host interface is a block which controls the transmission and reception of data to and from the host controller. it accepts communication control commands, passes on return codes, and forwards transmit data. the forwarding of transmit data takes place through the fifo buffers, 4 bytes of write data buffer (wdb) and 20 bytes of read data buffer (rdb). it also absorbs the differences between iebus transmission speed and the transmission speed on the serial interface between the m pd6708 and the host controller. logical status iebus signals 0 (bus+) C (busC) 3 120mv 1 (bus+) C (busC) 20mv
22 m pd6708 4. interfacing with host controller this chapter will explain the interfacing that occurs between the m pd6708 and the host controller. 4.1 accessible buffers and registers from host controller the host controller, which controls the m pd6708, can access the write data (wdb), the read data buffer (rdb), the command register (cmr), and the status register (str) within the m pd6708. 4.1.1 write data buffer (wdb) wdb is a 4-byte fifo buffer in which the host controller transmit data and the parameters of the communication control commands are written. 4.1.2 read data buffer (rdb) rdb is a 20-byte fifo buffer which stores the receive data acknowledged by the data link layer controller in the m pd6708. the host controller reads the m pd6708 receive data from rdb. 4.1.3 command register (cmr) cmr is an 8-bit register used to write control commands for the m pd6708. as shown in table 4-1, the host controller sets the reset mode and the host interface mode in higher 4 bits and sets the communication control command code in lower 4 bits. table 4-1. contents of command register bit value meaning bit 7 1 entering the reset mode 0 exiting the reset mode bit 6 1 data of lower 4 bits of cmr is valid. 0 data of lower 4 bits of cmr is not valid. bit 5 00 change of mode through pin control switches the host interface mode bit 4 01 data write mode 10 data read mode 11 status read mode bit 3 to set the communication control command codes bit 0
23 m pd6708 4.1.4 status register (str) str is an 8-bit register used to determine the status of the m pd6708. the statuses of wdb and rdb and the status of interrupts can be read from higher 4 bits. the return code, which indicates the result of the communication, can be read from lower 4 bits. table 4-2. contents of status register bit value meaning description bit 7 1 wdb is full indicates whether data can be written to wdb 0 wdb is not full bit 6 1 rdb is empty indicates whether data can be read from rdb 0 rdb is not empty bit 5 1 wdb is empty indicates whether data is in wdb 0 wdb is not empty bit 4 1 interrupt requested indicates whether interrupt servicing is being requested (bit 4 of the status 0 interrupt not requested register is reset by str by the host controller) bit 3 to return code return code will be read bit 0 4.2 host interface modes the host controller can access wdb, rdb, cmr, and str within the m pd6708 via the serial interface (sck, si, so). there are four modes for accessing the serial interface, as shown in the table 4-3. there are two method for switching among these four host interface modes: by using c/d pin and r/w pin, and by writing data to cmr (software control). table 4-3. host interface mode mode operation data write mode data input to si pin is written to wdb from msb at the rising edge of the serial clock input to sck pin. data setting is completed at the eighth serial clock cycle. data read mode rdb data is output from msb to so pin at the falling edge of the serial clock input to sck pin. a data read is completed by inputting eight serial clock cycles. data at si pin is ignored. command write mode data input to si pin is written to cmr from msb at rising edge of the serial clock input to sck pin. data setting is completed at the eight serial clock cycle. status read mode str data is output from msb to so pin at the falling edge of the serial clock input to sck pin. a data read is completed by inputting eight serial clock cycles. data at si pin is ignored.
24 m pd6708 4.2.1 switching through pin control with bits 5 and 4 of cmr both 0, the host interface mode can be switched by setting the c/d pin and r/w pin to the values shown in table 4-4. table 4-4. switching host interface mode by pin control c/d r/w host interface mode 0 0 data write mode 0 1 data read mode 1 0 command write mode 1 1 status read mode figure 4-1. example of host controller connections by pin control caution if the power supply voltage moves out of the 5 v 5 % range, the reset pin must be driven low for 6 m s or more in order to reset the m pd6708. iebus 120 w 120 w 5 v 12 mhz 5 v power supply voltage detection circuit pd6708 m v dd av dd bus+ bus xi xo gnd test sck si so irq c/d r/w cs reset sck so si int port port port host controller
25 m pd6708 figure 4-2. host interface timing by pin control cs c/d r/w sck si so cmr wdb higher 4 bits lower 4 bits undefined 00000000 0000 str contents undefined rdb contents undefined chip unselect command write mode status read mode data write mode data read mode
26 m pd6708 4.2.2 switching through software control with the c/d pin at the high level and the r/w pin at the low level, the host interface mode can be switched from the host controller by setting bits 5 and 4 of cmr to the values shown in table 4-5. table 4-5. switching host interface mode by software control bit 5 bit 4 host interface mode 0 0 mode switching by pin control 0 1 data write mode 1 0 data read mode 1 1 status read mode after one byte of data has been forwarded, the host interface mode will become the command write mode, which is controlled by the c/d and r/w pins. figure 4-3. example of host controller connections by software control iebus 120 w 120 w 5 v 12 mhz 5 v power supply voltage detection circuit pd6708 m v dd av dd bus+ bus xi xo gnd test sck si so irq c/d r/w cs reset sck so si int host controller 5 v
27 m pd6708 figure 4-4. host interface timing by software control remark connect c/d and r/w pins to v dd and gnd, respectively. sck si so cmr wdb higher 4 bits lower 4 bits undefined 0011 0011 str contents undefined command write mode status read mode command write mode data write mode 0001 0001
28 m pd6708 4.3 reset mode when the reset pin is driven low, the m pd6708 enters the reset mode. to release the reset mode, the reset pin must be driven high and a reset release command input. there are two methods of resetting the m pd6708, as follows. (1) resetting with reset pin if the reset pin is driven low, the m pd6708 will enter the reset mode. to exit the reset mode, drive the reset pin high and set bit 7 of cmr to 0. (2) resetting by software if bit 7 of cmr is set to 1 with the reset pin fixed high, the m pd6708 will enter the reset mode. to exit the reset mode, set bit 7 to 0. when powering on, the reset pin must be driven low to execute a reset. the m pd6708 will be in the following condition directly after leaving the reset mode. <1> iebus slave status is intialized. table 4-6. slave status values after leaving reset mode bit value meaning bit 7 1 up to mode 2 is supported bit 6 0 bit 5 0 always 0 bit 4 0 the slave transmission section has stopped. bit 3 0 always 0 bit 2 0 unit is not locked. bit 1 0 slave receive buffer is empty. bit 0 0 slave transmit buffer is empty. <2> wdb and rdb are empty. <3> reception is disabled. slave reception and broadcast reception are not acknowledged.
29 m pd6708 figure 4-5. example of reset control on powering on cs c/d r/w sck si so cmr higher 4 bits lower 4 bits undefined 0000 undefined reset mode power on command write mode reset 0 0 0 0 0 0 0 0
30 m pd6708 5. communication control commands the operation conditions of the m pd6708 can be controlled by giving it a command from the host controller. after a communication using the appropriate procedure (see 8.3.2 communication control command processing routine ), it is executed in a period in which communication is not being performed (standby state). 5.1 overview of communication control commands table 5-1. overview of communication control commands command name description init (initialize) sets local address and initializes. setsa (set slave address) sets the unit to communicate with. mreq1 (master request 1) communicates as a master unit. mreq2 (master request 2) continues in previous condition as the master unit and communicates. abort (abort) aborts communications. setsd (set slave data) sets data for slave transmission. getsta (get status) reads communication status. setrev (set receive) sets reception disabled state/enabled state. (1) write command the command codes and command parameters for the write commands are shown in table 5-2. table 5-2. command codes and command parameters of write commands note only set when transmitting. caution note that even if the host controller makes a mistake in setting the number of command parameter bytes, an error message will not be returned by the m pd6708, and command processing will be performed as though it were a correctly set command. command code command parameters (wdb) command name (lower 4 bits of cmr) first byte second byte third byte fourth byte init 0000 setsa 0001 mreq1 0010 mreq2 0011 abort 0100 setsd 0101 setrev 0111 control bits broad- cast bits unit address condition setting code slave address 0000 number of master master transmit master transmit transmit data bytes note data (first byte) note data (second byte) note number of slave slave transmit slave transmit slave transmit transmit data bytes data (first byte) data (second byte) data (third byte) reception status code msb lsb msb lsb msb lsb msb lsb msb lsb
31 m pd6708 (2) read command the command code of the read command is shown in table 5-3. table 5-3. command code of read command command code data placed in rdb after command execution command name (lower 4 bits of cmr) first byte second byte getsta 0110 lock status address of locked unit (12 bits) remark with a read command, the command execution result is placed in rdb, and therefore it is performed in the reception disabled state. 5.2 communication control command functions 5.2.1 init command (command code: 0000) (1) functions <1> unit address setting this command sets the unit address (12 bits), the unit address will be used as the master address when a unit is communicating as the master unit, and as the slave address when a unit is communicating as the slave. <2> condition setting ? the status of bit 4 of iebus slave status is set. slave transmission block operation enabled, stopped (bit 4) (setting of use/non-use of the function that transmits data to the master unit) ? the communication mode to be used is set. table 5-4. condition setting method condition setting code condition setting contents bits 3 and 2 00 communication performed in mode 0 01 communication performed in mode 1. 10 communication performed in mode 2. 11 undefined bit 1 0 fixed at 0 bit 0 0 slave transmission block stopped 1 slave transmission block operational the local-station address and condition setting contents set by init command retain their set values unless power is turned off or reset mode is entered (see 4.3 reset mode ). <3> slave status initialization the slave status is initialized as shown in table 5-5. msb lsb msb lsb msb lsb
32 m pd6708 table 5-5. slave status after execution of init command bit value meaning bit 2 0 unit is not locked. bit 0 0 slave transmit buffer is empty. <4> slave transmission and broadcast reception are enabled. <5> after the 2-byte command parameter (master address and condition setting code) have been read from the write data buffer (wdb), wdb is cleared. (2) example when init command specifies that the master address is 012h and the condition setting are communication in mode 1 and slave data transmission section operable, the contents of wdb and cmr are as shown below. 5.2.2 setsa command (command code: 0001) (1) functions <1> slave address (12 bits) setting the value for the slave address set by the setsa command remains unchanged until the power is turned off or the reset mode is entered. <2> this command clears wdb after reading the 2-byte command parameter (slave address) from wdb. (2) example when setsa command sets the slave address as 024h, the contents of wdb and cmr are as shown below. 0000 0001 0010 0101 0100 0000 first byte second byte master address condition setting code third byte fourth byte wdb cmr 0000 0010 0100 0000 0100 0001 first byte second byte slave address set to 0000 third byte fourth byte wdb cmr
33 m pd6708 5.2.3 mreq1 command (command code: 0010) (1) functions this command executes a master communication (transmission or reception). after execution of the command, the unit begins communication as the master unit. as long as it does not lose in arbitration, the master unit will communicate with the slave unit which has the slave address specified by setsa command. <1> selected broadcast communication or ordinary communication broadcast communication selection : 0h (broadcast bit 0 output) ordinary communication selection : 8h (broadcast bit 1 output) <2> sets the control bits (4 bits) <3> sets the number of transmit data bytes (8 bits) (transmission only) table 5-6. number of transmit data bytes setting number of transmit data bytes command parameter 1 byte 1h 2 bytes 2h :: :: 255 bytes ffh 256 bytes 00h <4> sets the transmit data (transmission only) (2) example when the mreq1 command is used to select ordinary communication, set the control bit to ah (command write and lock), the number of transmit data bytes to 4, and the transmit data to 12h, 34h, 56h, and 78h, the contents of wdb and cmr are shown below. caution transmit data 56h and 78h should be set when the above command parameters have been read and wdb is empty. 1000 1010 0000 0100 0100 0010 first byte second byte broadcast bits number of transmit data bytes third byte fourth byte wdb cmr control bits first data byte second data byte 0011 0010 0001 0100
34 m pd6708 5.2.4 mreq2 command (command code: 0011) (1) functions this command re-executes a master communication (transmission or reception). if master transmission or reception stops midway, the master communication is re-executed from the stopped condition. (2) command execution conditions if a communication control command other than an mreq2 command is executed after the master communication ends midway, the mreq1 command may not re-execute the communication correctly from the communication interrupted condition. (3) example when re-execution is performed by the mreq2 command when communication has been interrupted due to generation of a timing error after transmission of two bytes (12h and 34h) in mode 1, as in the mreq1 command example, the contents of wdb and cmr are as shown below. the previously set mreq1 command values are used for the broadcast bits, control bits and number of transmit data bytes. cautions 1. a master communication performed by execution of the mreq1 and mreq2 commands is performed in only one frame. however, if the unit loses in arbitration, the frame is automatically reset up twice (three times in total). 2. init command must be executed before setting the mreq1 or mreq2 command. if mreq1 or mreq2 is set before execution of init command, master communication will not be performed. 5.2.5 abort command (command code: 0100) (1) functions this command aborts master communications and slave unit data transmissions. <1> it clears the data placed in wdb. <2> it cancels the slave transmit data (setsd command). (2) example when the master unit begins communication as in the mreq1 command example, a communication error is generated and the two bytes of transmit data (12h and 34h) remaining in wdb are canceled by abort command, the contents of cmr are as shown below. 0101 0110 0111 1000 0100 0011 first byte second byte data to be transmitted upon re-execution of command third byte fourth byte wdb cmr
35 m pd6708 [before execution of abort command] [after execution of abort command] the data placed in wdb is cleared. 5.2.6 setsd command (command code: 0101) (1) functions this command specifies the data transmitted to the master unit when a data read and lock (control bits: 3h) or a data read (control bits: 7h) is received from the master unit. <1> sets the number transmit data bytes (8 bits) table 5-7. number of transmit data bytes number of transmit data bytes command parameter 1 byte 1h 2 bytes 2h :: :: 64 bytes 40h <2> sets the transmit data 0001 0010 0011 0100 0100 0100 first byte second byte third byte fourth byte wdb cmr first byte second byte third byte fourth byte wdb cmr
36 m pd6708 (2) validity of setsd command when setsd command is executed, it remains valid until one of the following cases arises. ? data read and lock (control bits: 3h) or data read (control bits: 7h) is received from the master unit. ? abort command is executed. ? power is turned off, or the reset mode is entered. when the setsd command is valid, wdb functions as the slave transmit buffer. caution the setsd command can be executed even if the unit is placed in the slave transmission selection halted state by init command. (3) example when the setsd command is used to set the number of transmit data bytes to 5, and the transmit data to abh, cdh, efh, 14h, and 25h, the contents of wdb and cmr are as shown below. caution transmit data 14h and 25h should be set when the above command parameters have been read and wdb is empty. 5.2.7 getsta command (command code: 0110) the getsta command is used by a unit to check whether it is locked by another unit. (1) functions <1> reads the lock status which indicates whether or not this unit is locked by another unit. 1j is placed in rdb if the unit is locked, and 0h if not locked. <2> the address (12 bits) of a locked unit is placed in rdb. this data is meaningless when the unit is not locked. after execution of getsta command, the data placed in rdb is as follows. 0000 0101 1010 1011 0100 0101 first byte second byte third byte fourth byte wdb cmr second data byte third data byte number of transmit data bytes first data byte 1100 1101 1110 1111 lock status address of locked unit (12 bits) first byte second byte msb lsb
37 m pd6708 (2) command setting conditions the reception disabled state must be set and rdb emptied before setting the getsta command. caution with the iebus, the lock function is provided to enable communication to run over a number of frames. however, if a locked unit goes down without being unlocked, the locked unit is unable to receive any further data. to avoid this situation, in a system which uses the lock function it is necessary to execute the getsta command periodically to monitor the lock status (a unit lock is released by executing init command). 5.2.8 setrev command (command code: 0111) (1) functions <1> set reception enabled/disabled status ? when reception status code is 00h : set to reception disabled status. in the reception disabled status, bit 1 of the slave status is 1, the slave receive buffer becomes virtually empty and no longer exists, and slave reception and broadcast reception are no longer performed. ? when reception status code is 01h : set to reception enabled status. when the prescribed conditions are met, slave reception and broadcast reception are performed. the reception enabled status is also set when a command other than setrev is executed. <2> this command clears wdb after reading the 1-byte command parameter (reception status code) from wdb.
38 m pd6708 6. return codes the m pd6708 sets the communication status as a return code in lower 4 bits of the status register (str) and requests an interrupt (irq output). as a result of the interrupt request from the m pd6708, the host controller can ascertain the communication result by reading the return code in the status read mode. 6.1 return codes in master/slave data transmission table 6-1 shows the return codes placed in the status register when a unit has executed the mreq1 or mreq2 command and becomes the master unit (including broadcast communication), and when the setsd command is executed and the slave unit transmits data. table 6-1. return codes in master/slave transmission return code name code description transmission start 0000 indicates that master/slave transmission will start. the point of generation differs between master transmission and slave transmission. <1> master transmission set when the master address field ends and the unit wins as the master unit. <2> slave transmission set when control bits (3h, 7h) which request data transmission are received from the master unit. transmission normal termination 0010 indicates that transmission of the number of data bytes specified by the message length bits has ended within one frame. termination during transmission 0011 indicates that the communication has ended without completion of transmission of the number of data bytes specified by the message length bits within one frame. in master transmission, termination during transmission is not flagged if the unit loses once in arbitration, and transmission is attempted up to three times. 6.2 return codes in master reception table 6-2 shows the return codes placed in str when a unit has executed the mreq1 or mreq2 command and becomes the master unit, and receives data, a status or lock address from a slave unit.
39 m pd6708 table 6-2. return codes in master reception return code name code description master reception start 0100 this return code is generated when the master unit correctly receives the message length code from the slave unit, informing the host controller of the start of master reception. master receive data full 0101 each time 20 bytes (rdb capacity) of master receive data is received, if rdb is full, this return code makes a request to the host controller for a read of receive data from rdb. master reception normal 0110 indicates that reception of the number of data bytes specified by the message termination length bits has ended within one frame. termination during master 0111 indicates that the communication has ended without completion of transmis- reception sion of the number of data bytes specified by the message length bits within one frame. termination during master reception is not flagged if the unit loses once in arbitration, and reception is attempted up to three times. 6.3 return codes in slave reception table 6-3 shows the return codes placed in str when data or a command is received from the master unit. table 6-3. return codes in slave reception return code name code description slave reception start 1000 this return code is generated when the slave unit correctly receives the message length codes from the master unit, informing the host controller of the start of slave reception. slave receive data full 1001 each time 20 bytes (rdb capacity) of slave receive data is received, if rdb is full, this return code makes a request to the host controller for a read of receive data from rdb. slave reception normal 1010 indicates that reception of the number of data bytes specified by the message termination length bits has ended within one frame. termination during slave 1011 indicates that the communication has ended without completion of transmis- reception sion of the number of data bytes specified by the message length bits within one frame. 6.4 return codes in broadcast reception table 6-4 shows the return codes placed in str when data or a command is received from the master unit in broadcast communication.
40 m pd6708 table 6-4. return codes in broadcast reception return code name code description broadcast reception start 1100 this return code is generated when the slave unit correctly receives the message length codes from the master unit, informing the host controller of the start of slave reception. broadcast receive data full 1101 each time 20 bytes (rdb capacity) of slave receive data is received, if rdb is full, this return code makes a request to the host controller for a read of receive data from rdb. broadcast reception normal 1110 indicates that reception of the number of data bytes specified by the message termination length bits has ended within one frame. termination during broadcast 1111 indicates that the communication has ended without completion of transmis- reception sion of the number of data bytes specified by the message length bits within one frame. 6.5 return codes generation intervals this section describes the generation order and the minimum generation interval for return codes generated each time communication is performed, each time a new return code is generated, it is placed in str without regard to str read. for this reason, the host controller must take account of the minimum return code generation interval in controlling the m pd6708. (1) master transmission after execution of the mreq1 or mreq2 command, the order of generation of master transmission return codes is as shown in figure 6-1. figure 6-1. return code generation order in master transmission the minimum generation intervals for return codes in master transmission are shown below. table 6-5. minimum generation intervals for return codes in master transmission ( m s) time mode 0 mode 1 mode 2 t1 approx. 6325 approx. 1605 approx. 1160 t2 approx. 10 approx. 10 approx. 10 t3 approx. 7290 approx. 2050 approx. 1550 transmission start (return code : 0000) termination during transmission (return code : 0011) transmission normal termination (return code : 0010) termination during transmission (return code : 0011) t3 t3 t3 new communication return codes ?slave reception start (return code : 1000) ?broadcast reception start (return code : 1100) etc. t1 t2
41 m pd6708 (2) slave transmission after execution of the setsd command, the order of generation of slave transmission return codes is as shown in figure 6-2. figure 6-2. return code generation order in slave transmission the minimum generation intervals for return codes in slave transmission are shown below. table 6-6. minimum generation intervals for return codes in slave transmission ( m s) time mode 0 mode 1 mode 2 t1 approx. 1580 approx. 400 approx. 290 t2 approx. 10 approx. 10 approx. 10 t3 approx. 7290 approx. 2050 approx. 1550 (3) master reception after execution of the mreq1 or mreq2 command, the order of generation of master reception returns codes is as shown in figure 6-3. figure 6-3. return code generation order in master reception the minimum generation intervals for return codes in master transmission are shown below. master reception start (return code : 0100) master receive buffer full (return code : 0101) t3 new communication return codes ?slave reception start (return code : 1000) ?broadcast reception start (return code : 1100) etc. t1 t2 termination during master reception (return code : 0111) t3 master reception normal termination (return code : 0110) termination during master reception (return code : 0111) t2 t1 master receive buffer full (return code : 0101) master reception normal termination (return code : 0110) termination during master reception (return code : 0111) t4 t4 t4 t4 t4 transmission start (return code : 0000) transmission normal termination (return code : 0010) termination during transmission (return code : 0011) t3 t3 new communication return codes ?slave reception start (return code : 1000) ?broadcast reception start (return code : 1100) etc. t1 t2
42 m pd6708 table 6-7. minimum generation intervals for return codes in master reception ( m s) time mode 0 mode 1 mode 2 t1 note approx. 8030 approx. 5800 t2 approx. 1580 approx. 400 approx. 290 t3 approx. 10 approx. 10 approx. 10 t4 approx. 7290 approx. 2050 approx. 1550 note the mode 0 master receive data consists of up to 19 bytes. there- fore, the receive buffer (20 bytes) does not become full, and a return code is not generated. (4) slave reception the order of generation of slave reception return codes is as shown in figure 6-4. figure 6-4. return code generation order in slave reception the minimum generation intervals for return codes in master transmission are shown below. table 6-8. minimum generation intervals for return codes in slave reception ( m s) note the mode 0 master receive data consists of up to 19 bytes. there- fore, the receive buffer (20 bytes) does not become full, and a return code is not generated. (5) broadcast reception the return code generation order and minimum generation intervals in the case of broadcast reception are the same as for (4) slave reception as shown above. time mode 0 mode 1 mode 2 t1 note approx. 8030 approx. 5800 t2 approx. 1580 approx. 400 approx. 290 t3 approx. 10 approx. 10 approx. 10 t4 approx. 7290 approx. 2050 approx. 1550 slave reception start (return code : 1000) slave receive buffer full (return code : 1001) t3 new communication return codes ?slave reception start (return code : 1000) ?broadcast reception start (return code : 1100) etc. t1 t2 t3 slave reception normal termination (return code : 1010) termination during slave reception (return code : 1011) t2 t1 slave receive buffer full (return code : 1001) slave reception normal termination (return code : 1010) termination during slave reception (return code : 1011) t4 t4 t4 t4
43 m pd6708 7. communicating with host controller this section explains the flow of data between the m pd6708 and the host controller via the serial interface (sck, so, si pins) during communications. 7.1 master transmission master transmission is the communication data exchange which takes place when a unit becomes a master unit by specifying ah, bh, and fh as control bits and executing the mreq1 or mreq2 command, and then transmitting data and commands to slave units. 7.1.1 master transmission by mreq1 command (1) the control bits, number of transmit data bytes and transmit data are placed in the write wdb as command parameters as shown in figure 7-1, and the mreq1 command (command code: 2h) is executed. (2) when a unit wins in arbitration as the master unit (the end of the master address field), the transmission start return code (0h) is placed in the status register (str), and an interrupt request is generated for the host controller. at this time, the host controller places the third and following bytes of transmit data in wdb. figure 7-1. data exchange during master transmission (contents of wdb) (3) if the number of data or command bytes specified by number of transmit data bytes are transmitted correctly, a transmission end return code (2h) will be placed in str and an interrupt request will be generated. (4) if an error occurs during transmission and the data communication is halted, a termination during transmission return code (3h) will be placed in str and an interrupt request will be generated. the timing at which the m pd6708 reads transmit data from wdb is shown below. table 7-1. timing for reading transmit data from wdb (the minimum time after transmission start return code (0h) is set in str) transmit data timing for reading transmit data from wdb ( m s) mode 0 mode 1 mode 2 transmit data (first byte) approx. 4745 approx. 1205 approx. 870 transmit data (second byte) approx. 6325 approx. 1605 approx. 1160 :::: transmit data (n-th byte) approx. 3165+1580 n approx. 805+400 n approx. 580+290 n broadcast bits control bits number of transmit data bytes first byte second byte third byte fourth byte wdb transmit data (first byte) transmit data (second byte)
44 m pd6708 7.1.2 master transmission by mreq2 command if the mreq1 command is executed and a communication error occurs during the transmission of data or a command, with the result that not all the data is transmitted, the remaining data can be transmitted by executing the mreq2 command. (1) the remaining data is placed in wdb as command parameters as shown in figure 7-2, and the mreq2 command (command code: 3h) is executed. figure 7-2. data exchange during master transmission (contents of write data buffer) transmit data (n-th byte) first byte second byte third byte fourth byte wdb transmit data (byte n+2) transmit data (byte n+3) transmit data (byte n+1) the remaining operations are the same as 7.1.1 master transmission by mreq1 command . 7.2 slave transmission 7.2.1 data transmission when the slave unit receives control bit 3h or 7h from the master unit, it transmits data as follows. (1) it places the number of transmit data bytes and transmit data in wdb as command parameters as shown in figure 7-3, and executes the setsd command (command code: 5h). (2) when the unit receives control bit 3h or 7h from the master unit, the transmission start return code (0h) is placed in str, and an interrupt request is generated. at this time, the host controller places the fourth and following bytes of transmit data in wdb. figure 7-3. data exchange during slave transmission (contents of wdb) first byte second byte third byte fourth byte wdb transmit data (second byte) transmit data (third byte) number of transmit data bytes transmit data (first byte) (3) if the number of data or command bytes specified by number of transmit data bytes is transmitted correctly, a transmission end return code (2h) will be placed in str and an interrupt request will be generated. (4) if an error occurs during transmission and the data communication is halted, a termination during transmission return code (3h) will be placed in str and an interrupt request will be generated. the timing at which the m pd6708 reads transmit data from wdb is shown below.
45 m pd6708 table 7-2. timing for reading transmit data from wdb (the minimum time after transmission start return code (0h) is set) transmit data timing for reading transmit data from wdb ( m s) mode 0 mode 1 mode 2 transmit data (first byte) approx. 1580 approx. 400 approx. 290 transmit data (second byte) approx. 3160 approx. 800 approx. 580 : ::: transmit data (n-th byte) approx. 1580 n approx. 400 n approx. 290 n 7.2.2 transmitting slave status address and lock address when the m pd6708 receives 0h, 4h, 5h, and 6h as control bits from the master unit, the slave status and lock address are generated automatically and sent to the master unit. as a result, there is no necessity for the host controller to be invol ved in the transmission of the slave status and lock address. 7.3 master reception when a unit becomes a master unit by setting 0h, 3h, 4h, 5h, 6h, and 7h as control bits and executing the mreq1 or mreq2 command, and receives data, slave status and lock address from the slave unit, the following will occur. (1) when the master unit returns an acknowledge in the message length field, the slave address, control bits and message length bits are placed in the read data buffer (rdb) by the mreq1 command as shown in figure 7-4, the master reception start return code (6h) is placed in str, and an interrupt request is generated. figure 7-4. data exchange during master reception (contents of rdb) (2) each time one byte of receive data is received, it is placed in rdb. (3) each time 20 bytes (rdb capacity) of receive data are received, if rdb is full, a master receive buffer full return code (5h) is placed in str, and an interrupt request is generated. (4) after one frame of data is placed in rdb, a master reception normal termination return code (6h) is placed in str and an interrupt request is generated. (5) if a communication error occurs during reception and communication stops without receiving all of the data transmitted from the slave unit, a termination during master reception return code (7h) is placed in str and an interrupt request is generated. the areas where m pd6708 places receive data, etc., in rdb are shown below. slave address (12 bits) first byte second byte third byte fourth byte onward rdb message length bits control bits
46 m pd6708 table 7-3. placing receive data in rdb parameter/ areas where rdb is read time ( m s) note communication data mode 0 mode 1 mode 2 slave address when ack bit is transmitted in message length field 00 0 control bits message length bits receive data (first byte) when first ack bit is transmitted in data field approx. 1580 approx. 400 approx. 290 receive data (second byte) when second ack bit is transmitted in data field approx. 3160 approx. 800 approx. 580 receive data (n-th byte) when n-th ack bit is transmitted in data field approx. 1580 n approx. 400 n approx. 290 n note minimum time after the master reception start return code is placed in str and an interrupt request is generated. 7.4 slave reception if a slave unit receives ah, bh, eh, or fh as control bits from the master unit and receive data or a command, the following will occur. (1) when the slave unit returns an acknowledge in the message length field, the master address, control bits and message length bits are placed in rdb as shown in figure 7-5, a slave reception start return code (8h) is placed in str, and an interrupt request is generated. figure 7-5. data exchange during slave reception (contents of rdb) (2) each time one byte of receive data is received, it is placed in rdb. (3) each time 20 bytes (rdb capacity) of receive data are received, if rdb is full, a slave receive buffer full return code (9h) is placed in str, and an interrupt request is generated. (4) after the final data of one frame is placed in rdb, a slave reception normal termination return code (ah) is placed in str and an interrupt request is generated. (5) if a communication error occurs during reception and communication stops without receiving all of the data transmitted from the master unit, a termination during slave reception return code (bh) is placed in str and an interrupt request is generated. the areas where the m pd6708 places receive data, etc., in rdb are shown below. master address (12 bits) first byte second byte third byte fourth byte onward rdb message length bits control bits
47 m pd6708 table 7-4. placing receive data in rdb parameter/ areas where rdb is read time ( m s) note communication data mode 0 mode 1 mode 2 master address when ack bit is received in message length field 0 0 0 control bits message length bits receive data (first byte) when first ack bit is received in data field approx. 1580 approx. 400 approx. 290 receive data (second byte) when second ack bit is received in data field approx. 3160 approx. 800 approx. 580 receive data (n-th byte) when n-th ack bit is received in data field approx. 1580 n approx. 400 n approx. 290 n note minimum time after the slave reception start return code is placed in str and an interrupt request is generated. 7.5 broadcast reception (1) when a broadcast reception unit receives the message length field, the master address, control bits and message length bits are placed in rdb as shown in figure 7-6, a broadcast reception start return code (ch) is placed in str, and an interrupt request is generated. figure 7-6. data exchange during broadcast reception (contents of rdb) (2) each time one byte of receive data is received, it is placed in rdb. (3) each time 20 bytes (rdb capacity) of receive data are received, if rdb is full, a slave receive buffer full return code (dh) is placed in str, and an interrupt request is generated. (4) after the final data of one frame is placed in rdb, a broadcast reception normal termination return code (eh) is placed in str and an interrupt request is generated. (5) if a communication error occurs during reception and communication stops without receiving all of the data transmitted from the master unit, a termination during broadcast reception return code (fh) is placed in str and an interrupt request is generated. the areas where the m pd6708 places receive data, etc., in rdb are the same as those shown in table 7-4. master address (12 bits) first byte second byte third byte fourth byte onward rdb message length bits control bits
48 m pd6708 8. example of host controller processing flow this chapter presents an example of the host controller processing flow for controlling the m pd6708 via the serial interface (sck, so, and si pins). the host controller processing flow comprises the following routines. ? main routine ? interrupt service routine 8.1 main routine note the equipment control routine is a routine which performs host controller application processing. when controlling the m pd6708, set the crq flag when there is a command request. see 8.3.1 start equipment initialization pd6708 initialization routine m crq note 1 0 command processing routine equipment control routine note normal end see 8.3.2 exit
49 m pd6708 8.2 interrupt service routine this routine is used when an interrupt request is generated from the m pd6708 (when irq pin becomes high). this routine reads the contents of the return code, performs flag setting, and reads receive data. notes 1. see 8.3.3. 2. see 8.3.4. 3. see 8.3.5. start disable interrupts from pd6708 m is sio register used? save value of i/o port which controls pd6708 c/d and r/w pins, and value of sio register in host controller m read str return code classification 01 master reception processing routine note 3 master transmission processing routine note 1 slave data transmission processing routine note 2 master? slave reception processing routine broadcast reception processing routine 10 11 restore value of i/o port which controls pd6708 c/d and r/w pins, and value of sio register in host controller m enable interrupts from pd6708 end reti m 00 yn y n this processing is not necessary if interrupts are disabled when sio is used in the main routine. most significant 2 bits of return code
50 m pd6708 8.3 processing routine 8.3.1 m pd6708 initialization routine ? init command setting flow start drive the host controller port which controls the pd6708 reset pin low for 6 s or longer, then return it to high. (not necessary when a hardware reset such as a power-on reset is executed.) reset pd6708 m cmr ? 00h init command setting normal end m place 00h in the command register. release reset mode. set unit address slave unit condition with init command. m start read str wdb empty? write to wdb write to wdb write to cmr normal end exit n y unit address setting (higher 8 bits) unit address (lower 4 bits) slave unit condition setting set command code (0h).
51 m pd6708 8.3.2 communication control command processing routine this processing routine sets the m pd6708 communication control commands setsa, mreq1, mreq2, abort, getsa, and setrev. processing starts when there is a command request during equipment control (crq = 1) (1) setsa command start read str wdb empty? write to wdb write to wdb write to cmr normal end exit n y slave address setting (higher 8 bits) slave address (lower 4 bits) communication mode setting set command code (1h).
52 m pd6708 (2) mreq1 command when msb of the control bits is 1 (master transmission) start read str wdb empty? write to wdb write to wdb write to wdb normal end exit n y set broadcast bits and control bits. set number of master transmit data bytes. set master transmit data (first byte). write to wdb n1 ? (number of master transmit data bytes) ?2 write to cmr set master transmit data (second byte). set command code (2h).
53 m pd6708 (3) mreq2 command after master transmission ends midway (4) mreq1 command when msb of the control bits is 0 (master reception) start read str wdb full? write to cmr normal end write to wdb n y set master transmit data. set command code (3h). start read str wdb and rdb empty? write to wdb normal end write to cmr exit n y set broadcast bits and control bits. set command code (2h).
54 m pd6708 (5) mreq2 command when master reception ends midway (6) abort command start read str wdb and rdb empty? normal end write to cmr exit n y set command code (3h). start normal end write to cmr set command code (4h).
55 m pd6708 (7) setsd command start read str wdb empty? write to wdb write to wdb write to wdb normal end exit n y set number of slave transmit data bytes. set slave transmit data (first byte). set slave transmit data (second byte). write to wdb n2 ? (number of slave transmit data bytes) ?3 write to cmr set slave transmit data (third byte). set command code (5h). slave transmission timer setting if the slave data transmission processing shown in 8.3.4 cannot be completed because control bits (3h, 7h) requesting slave data transmission were not received from the master unit within the prescribed time, an abort command is executed and slave data transmission is exited.
56 m pd6708 (8) getsta command start read str wdb empty? write to wdb normal end exit n y set reception status code (reception disabled : 00h). write to cmr read str wdb and rdb empty? write to cmr n y read str rdb empty? read rdb read rdb y n set setrev command code (7h). set getsta command code (6h). read lock status (4 bits) and lock address (higher 4 bits). read lock address (higher 8 bits).
57 m pd6708 8.3.3 master transmission processing routine this processing routine is used when a unit becomes the master unit after executing the mreq1 or mreq2 command and transmits data and commands to a slave unit. this routine is an interrupt service routine, and is executed when the return code (higher 2 bits = 00) is read in master transmission. notes 1. to transmit the remaining data, execute the mreq2 command (see 8.3.2 (3) ). to abort master transmission, execute the abort command (see 8.3.2 (6) ). 2. n1: number of master transmit data bytes. start read str return code 3h? n1 = 0 normal end n y set master transmit data. wdb full? write to wdb n note 2 return code 2h? y n y note 1 termination during transmission n1 ? n1 ?1 note 2 n y
58 m pd6708 8.3.4 slave data transmission processing routine this processing routine is used when a slave unit transmits data to the master unit after setting the setsd command. this routine is an interrupt service routine, and is executed when the return code (higher 2 bits = 00) is read in slave data transmission. notes 1. untransmitted data in wdb is cleared by executing the abort command (see 8.3.2 (6) ). 2. n2: number of slave transmit data bytes start read str return code 3h? n2 = 0 normal end n y set slave transmit data. wdb full? write to wdb n note 2 return code 2h? y n y note 1 termination during transmission n2 ? n2 ?2 note 2 n y
59 m pd6708 8.3.5 master reception processing routine this processing routine is used when the master unit receive data, slave status and lock address after execution of the mreq1 or mreq2 command. one of four different routines is executed depending on the contents of the return code. (1) processing in case of master reception start return code (4h) start mre ? 1 read rdb read rdb read rdb normal end read slave address (higher 8 bits). read slave address (lower 4 bits) and control bits. read number of master receive data bytes. n3 ? number of master receive data bytes set master reception flag (mre).
60 m pd6708 (2) processing in case of master receive buffer full return code (5h) note n3: number of master receive data bytes start i ? 20 read rdb set master receive buffer size. i ? i ?1 i = 0 ? n3 ? n3 ?1 note n y end read master receive data.
61 m pd6708 (3) processing in case of master reception normal end return code (6h) start mre = 1 ? set master reception flag (mre). mre ? 1 y read rdb read rdb read rdb n3 ? number of master receive data bytes read rdb n3 = 0 ? n3 ? n3 ?1 n n y read slave address (higher 8 bits). read slave address (lower 4 bits) and control bits. read number of master receive data bytes. read master receive data. end mre ? 0
62 m pd6708 (4) processing in case of end during master reception return code (7h) note to distinguish data from receive data (slave reception, broadcast reception) newly input in the next communication frame, after reading rdb (inputting one serial clock pulse to sck pin), str should be read (inputting one serial clock pulse to sck pin) within the time shown below. ? when the next frame is mode 2 : approx. 290 m s ? when the next frame is mode 1 : approx. 400 m s ? when the next frame is mode 0 : approx. 1580 m s however, the above time limits for reading str do not apply if this processing routine is executed in the reception disabled state after executing the setrev command. the flowcharts for slave reception processing and broadcast reception processing are the same as for master reception processing, and are therefore omitted here. start mre = 1 ? set master reception flag (mre). mre ? 1 note y read rdb read rdb read rdb n3 ? number of master receive data bytes read str rdb empty ? read rdb n n mre ? 0 end y read slave address (higher 8 bits). read slave address (lower 4 bits) and control bits. read number of master receive data bytes. read master receive data.
63 m pd6708 parameter symbol test conditions ratings unit power supply v dd , av dd | v dd C av dd | < 0.5 v C0.5 to +7.0 v logic input voltage v i the pin without bus+ and busC C0.5 to v dd + 0.3 v logic output voltage v o C0.5 to v dd + 0.3 v bus input voltage v bi bus+ and busC C0.5 to + 6.0 v bus output voltage v bo C0.5 to + 6.0 v operating ambient temperature t a C40 to + 85 c storage temperature t stg C65 to + 150 c 9. electrical specifications absolute maximum ratings (t a = 25 c) dc characteristics (t a = e40 to +85 c, v dd = av dd = 5 v 10 %) parameter symbol test conditions min. typ. max. unit input voltage high v ih 0.8v dd v dd v input voltage low v il 0 0.2v dd v output voltage high v oh i oh = C400 m a 0.7v dd v output voltage low v ol i ol = 2.5 ma 0.4 v input leakage current high i lih v i = v dd 10 m a input leakage current low i lil v i = 0 v C10 m a output leakage current high i loh v o = v dd 10 m a output leakage current low i lol v o = 0 v C10 m a supply current i dd1 carrier sense 3.5 10 ma i dd2 reset mode 1.2 3 ma capacitance characteristics (t a = 25 c, v dd = av dd = 0 v) parameter symbol test conditions min. typ. max. unit input capacitance c i fc = 1 mhz, 15 pf input/output capacitance c io unmeasured pins returned to 0 v 15 pf
64 m pd6708 recommended ceramic resonator (12 mh z ) recommended crystal resonator (12 mh z ) manufacturer product name external capacities [pf] c1 c2 murata mfg. cst12.0mt note 1 CC CC csa12.00mx241 30 30 kyocera corp. kbr-12.0m note 2 33 33 manufacturer product name external capacities [pf] c1 c2 kinseki, ltd hc-49/u 22 22 recommended ceramic resonator (12.58 mh z ) manufacturer product name external capacities [pf] c1 c2 murata mfg. cstcs12.5mta 904 note 1 CC CC tdk fcr12.58m2s note 1 33 33 notes 1. can only be used when communication mode 0 or 1 is used (frequency accuracy: 1.5 %). 2. this is a custom product, and therefore the manufacturer should be contacted directly. caution the oscillation circuit constants and oscillation voltage range shown above indicate the condition under which oscillation is stable and do not guarantee the oscillation frequency accuracy. if a high oscillation frequency accuracy is required from the actual circuit, the resonator mounted to the actual circuit must be adjusted. for details, directly consult the manufacturer of the resonator. external circuit caution wire the dotted portion in the above figure as follows to prevent adverse influences of wiring capacitance when using the system clock oscillation circuit. ? keep the wiring length as short as possible. ? do not cross the wiring with any other signal lines. ? do not place the wiring in the vicinity of a line through which a high alternating current flows. ? always keep the ground point of the capacitor of the oscillation circuit at the same potential as v ss . ? do not ground the wiring to a ground pattern through which a high current flows. ? do not extract signals from the oscillation circuit. xi xo gnd c1 c2 h h h
65 m pd6708 parameter symbol test conditions min. typ. max. unit system clock f x = 12 mhz using communication mode 2 11.94 12.00 12.06 mhz using communication mode 0,1 11.82 12.00 12.18 mhz f x = 12.58 mhz using communication mode 2 12.52 12.58 12.64 mhz using communication mode 0,1 12.40 12.58 12.76 mhz sck cycle time t kcy 0.8 m s sck high-level width t kh 0.4 m s sck low-level width t kl 0.4 m s si setup time (to sck - )t sik 100 ns si hold time (from sck - )t ksi 400 ns so output delay time (from sck - ) t kso 300 ns cs, c/d, r/w setup time (to sck - ) t sa 0ns cs, c/d, r/w hold time (from sck - ) t ha 400 ns cs high-level width 400 ns irq output high-level width 8 11 m s reset low-level width 6 m s oscillation stabilization time t os f x = 12 mhz 20 ms ac characteristics (t a = C40 to +85 c, v dd = av dd = 5 v 10 %) serial transfer timing cs, c/d, r/w sck si so t sa t ha t kyc t kl t kh t sik t ksi data input data output t kso
66 m pd6708 parameter symbol test conditions min. typ. max. unit output current high i oh r l = 60 w 5 % C 2.73 C 6.22 ma output current low i ol 1.0 m a in-phase output voltage v ocom when high and low v input voltage high v ih 120 mv input voltage low v il 20.0 mv input hysteresis voltage v ihys 25 mv in-phase input voltage high v ihcom 1.00 v dd C 1.0 v in-phase input voltage low v ilcom 0v dd v driver output resistance r o between bus + and bus C 100 k w driver output capacitance c o between bus + and bus C, 25 pf receiver input capacitance c i between bus + and gnd, 25 pf between bus C and gnd iebus driver/receiver characteristics (t a = C40 to +85 c, v dd = av dd = 5 v 10 %) 2 v dd C0.25 2 v dd +0.25 2 v dd
67 m pd6708 10. package drawings h 16 pin plastic dip (300 mil) item millimeters inches a b c f g h i j k 20.32 max. 2.54 (t.p.) 3.5?.3 0.51 min. 4.31 max. 1.27 max. l 0.25 7.62 (t.p.) 5.08 max. 6.5 n 1.1 min. p 0.800 max. 0.050 max. 0.043 min. 0.138?.012 0.020 min. 0.170 max. 0.200 max. 0.300 (t.p.) 0.256 0.01 0.043 min. 0.100 (t.p.) 1.1 min. p16c-100-300b-1 d 0.50?.10 0.020 m 0.25 0.010 +0.10 ?.05 r0 ~ 15 0 ~ 15 +0.004 ?.005 +0.004 ?.003 notes each lead centerline is located within 0.25 mm (0.01 inch) of its true position (t.p.) at maximum material condition. item "k" to center of leads when formed parallel. 1) 2) m 18 16 9 a b i j g h c n f d m r k l p
68 m pd6708 16 pin plastic sop (300 mil) item millimeters inches a b c e f g h i j 10.46 max. 1.27 (t.p.) 1.8 max. 1.55 7.7?.3 0.78 max. 0.12 1.1 5.6 m 0.1?.1 n 0.412 max. 0.031 max. 0.004?.004 0.071 max. 0.061 0.303?.012 0.220 0.043 0.005 0.050 (t.p.) p16gm-50-300b-4 p3 3 +7 note each lead centerline is located within 0.12 mm (0.005 inch) of its true position (t.p.) at maximum material condition. d 0.40 0.016 +0.10 ?.05 k 0.20 0.008 +0.10 ?.05 l 0.6?.2 0.024 0.10 ? +7 ? 0.004 +0.008 ?.009 +0.004 ?.002 +0.004 ?.003 a c d g p detail of lead end f e b h i l k m m 18 9 16 j n
69 m pd6708 11. recommended soldering conditions this product should be soldered and mounted under the conditions recommended in the table below. for details of recommended soldering conditions, refer to the information document semiconductor device mounting technology manual (iei-1207) . for soldering methods and conditions other than those recommended, please contact nec representative. table 11-1. surface mount type soldering conditions m pd6708gs : 16-pin plastic sop (300 mil) caution use of more than one soldering method should be avoided (except for partial heating). table 11-2. hole-through type soldering conditions m pd6708cx : 16-pin plastic dip (300mil) soldering method soldering conditions wave soldering solder temperature: 260 c or below, flow time: 10 seconds or less (pin only) partial heating pin temperature: 300 c or below, flow time: 3 seconds or less (per pin) caution wave soldering is used on the pin only, and care must be taken to prevent solder from coming into direct contact with the package body. h soldering method soldering conditions symbol infrared ray reflow package peak temperature: 230 c, reflow time: 30 seconds or less (at 210 c or ir30-00-1 higher), number of reflow processes: 1 vps reflow package peak temperature: 215 c, reflow time: 40 seconds or less (at 200 c or vp15-00-1 higher), number of reflow processes: 1 partial heating pin temperature: 300 c or below, flow time: 3 seconds or less (per side of device) CC
70 m pd6708 appendix major differences between m pd6708 and m pd72042a, m pd72042b part number m pd6708 m pd72042a m pd72042b parameter oscillation frequency (f x ) 12 mhz 6 mhz supply voltage (v dd )5 v 10 % operating ambient temperature (t a ) C40 to +85 ?c iebus communication mode modes 0, 1, and 2 driver/receiver provided external protection resistor not necessary necessary (connect 180 w in series to bos+ and bosC) transmit buffer 4 bytes 33 bytes receive buffer 20 bytes 40 bytes interfacing with microcontroller note serial interface (3-wire) serial interface (3-wire/2-wire) msb first msb first lsb first package 16-pin sop (300 mil) 16-pin sop (375 mil) 16-pin dip (300 mil) note setting commands/data and related pins differs between the m pd6708 and m pd72042a, m pd72042b. h
71 m pd6708 notes for cmos devices 1 precaution against esd for semiconductors note: strong electric field, when exposed to a mos device, can cause destruction of the gate oxide and ultimately degrade the device operation. steps must be taken to stop generation of static electricity as much as possible, and quickly dissipate it once, when it has occurred. environmental control must be adequate. when it is dry, humidifier should be used. it is recommended to avoid using insulators that easily build static electricity. semiconductor devices must be stored and transported in an anti-static container, static shielding bag or conductive material. all test and measurement tools including work bench and floor should be grounded. the operator should be grounded using wrist strap. semiconductor devices must not be touched with bare hands. similar precautions need to be taken for pw boards with semiconductor devices on it. 2 handling of unused input pins for cmos note: no connection for cmos device inputs can be cause of malfunction. if no connection is provided to the input pins, it is possible that an internal input level may be generated due to noise, etc., hence causing malfunction. cmos device behave differently than bipolar or nmos devices. input levels of cmos devices must be fixed high or low by using a pull-up or pull-down circuitry. each unused pin should be connected to v dd or gnd with a resistor, if it is considered to have a possibility of being an output pin. all handling related to the unused pins must be judged device by device and related specifications governing the devices. 3 status before initialization of mos devices note: power-on does not necessarily define initial status of mos device. production process of mos does not define the initial operation status of the device. immediately after the power source is turned on, the devices with reset function have not yet been initialized. hence, power-on does not guarantee out-pin levels, i/o settings or contents of registers. device is not initialized until the reset signal is received. reset operation must be executed imme- diately after power-on for devices having reset function.
m pd6708 no part of this document may be copied or reproduced in any form or by any means without the prior written consent of nec corporation. nec corporation assumes no responsibility for any errors which may appear in this document. nec corporation does not assume any liability for infringement of patents, copyrights or other intellectual property rights of third parties by or arising from use of a device described herein or any other liability arising from use of such device. no license, either express, implied or otherwise, is granted under any patents, copyrights or other intellectual property rights of nec corporation or others. while nec corporation has been making continuous effort to enhance the reliability of its semiconductor devices, the possibility of defects cannot be eliminated entirely. to minimize risks of damage or injury to persons or property arising from a defect in an nec semiconductor device, customer must incorporate sufficient safety measures in its design, such as redundancy, fire-containment, and anti-failure features. nec devices are classified into the following three quality grades: standard, special, and specific. the specific quality grade applies only to devices developed based on a customer designated quality assurance program for a specific application. the recommended applications of a device depend on its quality grade, as indicated below. customers must check the quality grade of each device before using it in a particular application. standard:computers, office equipment, communications equipment, test and measurement equipment, audio and visual equipment, home electronic appliances, machine tools, personal electronic equipment and industrial robots special: transportation equipment (automobiles, trains, ships, etc.), traffic control systems, anti-disaster systems, anti-crime systems, safety equipment and medical equipment (not specifically designed for life support) specific: aircrafts, aerospace equipment, submersible repeaters, nuclear reactor control systems, life support systems or medical equipment for life support, etc. the quality grade of nec devices in standard unless otherwise specified in nec's data sheets or data books. if customers intend to use nec devices for applications other than those specified for standard quality grade, they should contact nec sales representative in advance. anti-radioactive design is not implemented in this product. m4 94.11 iebus and inter equipment bus are trademarks of nec corporation. the export of this product from japan is prohibited without governmental license. to export or re-export this product from a country other than japan may also be prohibited without a license from that country. please call an nec sales representative.

▲Up To Search▲

Price & Availability of UPD6708CX

	To Download UPD6708CX Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .